Please re-use the test.yaml instead of creating dedicated workflow files. If you want to organize them in individual files, try a design like this.

The main thing is that we should be gating different stages of the CI, e.g. always check a pre-commit first before doing long tests.

Please no conda/mamba. If you wish to check it make it a distinct test set. Instead for windows please use vcpkg as the package manager.

The use of micromamba was to easily get the dependencies, I don't have the need to test it specifically and can use whatever you prefer. Out of curiosity, why are you opposed to using micromamba?

Out of curiosity, why are you opposed to using micromamba?

Mostly that it is the wrong tool in CI. If the purpose is to test the conda ecosystem then it can make sense for that, but then it would be better to have the project packaged there. But for testing OS, using the primary package manager of that OS would be preferred, particularly important being the usage of the native compilers, in this case being msvc.

The use of micromamba was to easily get the dependencies

We are using FetchContent in order to have a package manager independent source of dependencies. Testing the package managers is also quite important since it can have specific patches applied, but in that case only the packaged packages must be used.

Modern approach is to use CMake presets, and I believe this one already has it.

Should be more explicit if you are testing FetchContent dependencies or package manager ones.